Database system, method of managing database, and computer-readable storage medium

ABSTRACT

The database system includes: a storage unit that stores a database including an entity data group and a plurality of identifier tables having only a plurality of fixed-length data; and a data processing unit that receives a query and performs data processing on the database on the basis of the received query. Each of the identifier tables includes at least one tuple that is defined in a row direction and at least one attribute field that is defined in a column direction and includes a plurality of data identifiers uniquely indicating the plurality of entity data as the fixed-length data. The database includes a link table that connects the tuples between the identifier tables, in addition to the plurality of identifier tables. The data processing unit performs the data processing using the link table and the identifier tables.

The present application is the National Phase of PCT/JP2009/002359,filed May 28, 2009, which claims priority based on Japanese PatentApplication No. 2008-143767, filed May 30, 2008 and Japanese PatentApplication No. 2008-249042, filed Sep. 26, 2008, the content of whichis incorporated herein by reference.

TECHNICAL FIELD

The present invention relates to a database structure and a techniquefor processing data in a database.

BACKGROUND ART

A relational database management system (RDBMS) is based on a relationalmodel theory proposed by Edgar Frank Codd (E. F. Codd) in 1970 and hasbeen widely used. A relational database (RDB) is an aggregate of aplurality of tables (that is, relations), and each table includes atleast one row (tuple) and at least one column (attribute field). Forexample, there is Patent Document 1 (Japanese Laid-Open PatentPublication No. 2005-208757) as a related art document about RDBMS.

However, in a general RDBMS, when a data processing amount increases anda processing load increases, a reduction in the processing speed oftransactions is noticeable. One of the causes of the reduction in theprocessing speed is that, when a search is performed for the tableforming the RDB for each row having a variable data length, it takes along time to calculate a data reading position, as compared to when thedata length of each row is fixed.

In addition, RDBMS manages data for each row using a unique key.Therefore, it is possible to effectively perform a large number ofprocesses for each row at the high speed, but it is difficult toeffectively perform a large number of processes for each column. Forexample, when processing data for each column, RDBMS needs to read aplurality of rows of data corresponding to a column required by a query,which causes a reduction in the processing speed. RDBMS can write eachrow of data to continuous storage areas of a memory. Therefore, it ispossible to access each row of data at a high speed. However, when RDBMSperforms a transaction related to, for example, a search process foreach column, a comparison operation, or an aggregate calculation, accessto data stored in a plurality of discontinuous memory areas is likely tooccur frequently, which results in a reduction in the processing speed.

A system called a data warehouse (DWH) has been used as a databasesystem that effectively performs a search process or an aggregateprocess on a large amount of data. However, DWH is a system that isconstructed independently from basic business systems and does notupdate data (add new data, change the existing data, or remove theexisting data) in principle. Therefore, DWH does not have a databasestructure capable of effectively updating data.

In order to solve the problems of RDBMS or DWH according to the relatedart, for example, Patent Document 2 (Japanese Laid-Open PatentPublication No. 2000-339390) and Patent Document 3 (Pamphlet ofInternational Publication No. WO 00/10103) disclose database systems.The database systems disclosed in Patent Document 2 and Patent Document3 use a database structure obtained by converting logical tabular datainto a plurality of information blocks corresponding to items, forexample, sex, age, height, and weight. Each of the information blocksincludes a value management table (value list) and an array of pointersto the value management table. The array of the pointers to the valuemanagement table means an array in which item value numbers (that is,the pointers to the value management table) in a certain column oftabular data are stored in a predetermined order (the order of recordnumbers) of the tabular data.

However, in the database structure disclosed in Patent Document 2 andPatent Document 3, the item value numbers in the value management tableneed to be arranged in a predetermined order. Therefore, when a new itemvalue number is inserted into the value management table during theupdate of data (for example, the update, insertion, or removal ofrecords), it is necessary to rearrange other existing item valuenumbers. In addition, the array of the pointers to the value managementtable needs to be updated such that the pointers are matched with therearranged item value numbers. Therefore, in the database structuredisclosed in Patent Document 2 and Patent Document 3, it is impossibleto effectively update data at a high speed. In particular, when data isfrequently updated, a processing load is very large and the processing,speed is significantly reduced.

-   [Patent Document 1] Japanese Laid-Open Patent Publication No.    2005-208757-   [Patent Document 2] Japanese Laid-Open Patent Publication No.    2000-339390-   [Patent Document 3] Pamphlet of International Publication No. WO    00/10103

DISCLOSURE OF THE INVENTION

The invention has been made in view of the above-mentioned problems andan object of the invention is to provide a database system, a method ofmanaging a database, a database structure, and a computer programcapable of effectively updating data in a database at a high speed.

According to the present invention, there is provided a database systemincluding: a storage unit that stores a database including an entitydata group containing a plurality of entity data and a plurality ofidentifier tables having only a plurality of fixed-length data; and adata processing unit that receives a query and performs data processingon the database on the basis of the received query. In the databasesystem, each of the identifier tables includes at least one tuple thatis defined in a row direction and at least one attribute field that isdefined in a column direction and includes a plurality of dataidentifiers uniquely indicating the plurality of entity data as thefixed-length data. The database includes a link table that connects thetuples between the identifier tables, in addition to the plurality ofidentifier tables. The data processing unit performs the data processingusing the link table and the identifier tables.

According to the present invention, there is provided a method ofmanaging a database including: a step of receiving a query for adatabase including an entity data group containing a plurality of entitydata and a plurality of identifier tables having only a plurality offixed-length data; and a step of performing data processing on thedatabase on the basis of the received query. Each of the identifiertables includes at least one tuple that is defined in a row directionand at least one attribute field that is defined in a column directionand includes a plurality of data identifiers uniquely indicating theplurality of entity data as the fixed-length data. The database includesa link table that connects the tuples between the identifier tables, inaddition to the plurality of identifier tables. The data processing isperformed using the link table and the identifier tables.

According to the present invention, there is provided a databasestructure including: an entity data group that includes a plurality ofentity data; a plurality of identifier tables that has only a pluralityof fixed-length data; and a link table that associates the identifiertables. In the data structure, each of the identifier tables includes atleast one tuple that is defined in a row direction and at least oneattribute field that is defined in a column direction and includes aplurality of data identifiers uniquely indicating the plurality ofentity data as the fixed-length data. The link table connects the tuplesbetween the identifier tables.

According to the present invention, there is provided a computer programthat causes a computer to execute a database management process. Thedatabase management process includes: a process of receiving a query fora database including an entity data group containing a plurality ofentity data and a plurality of identifier tables having only a pluralityof fixed-length data; and a process of performing data processing on thedatabase on the basis of the received query. Each of the identifiertables includes at least one tuple that is defined in a row directionand at least one attribute field that is defined in a column directionand includes a plurality of data identifiers uniquely indicating theplurality of entity data as the fixed-length data. The database includesa link table that connects the tuples between the identifier tables, inaddition to the plurality of identifier tables. The data processing isperformed using the link table and the identifier tables.

As described above, the database system according to the inventionincludes the database including an entity data group and an identifiertable having the fixed-length data identifiers that uniquely indicate aplurality of entity data in the entity data group. Therefore, forexample, when specific entity data in the entity data group is updatedin response to a query, it is possible to update the database only byupdating a data identifier corresponding to the updated entity data.

When entity data is added (inserted) to the entity data group inresponse to a query, it is possible to update the database only byadding a data identifier corresponding to the added entity data to theidentifier table.

When entity data is removed from the entity data group in response to aquery, it is possible to update the database only by removing a dataidentifier corresponding to the removed entity data from the identifiertable. As such, when the entity data is updated, added, or removed, theidentifier table is updated in the minimum range. Therefore, it ispossible to effectively update the database at a high speed.

The method of managing a database and the computer program according tothe invention can effectively update the database at a high speed sincethey perform the update process on the database.

The database structure according to the invention can be applied to thedatabase incorporated into the database system. In addition, thedatabase structure can be applied to the database used in the databasemanagement method or the computer.

It is possible to effectively update a database at a high speed.

BRIEF DESCRIPTION OF THE DRAWINGS

The above-mentioned objects, objects other than them, characteristics,and advantages will become more apparent by the accompanying drawingsand the following preferred exemplary embodiments.

FIG. 1 is a functional block diagram illustrating the schematicstructure of a database system according to an exemplary embodiment ofthe invention;

FIG. 2 is a flowchart schematically illustrating the procedure of theprocess of a transaction processing unit of a database system;

FIG. 3 is a diagram schematically illustrating an example of a databasestructure according to a first exemplary embodiment of the invention;

FIG. 4 is a diagram illustrating the storage of data identifiers incontinuous storage areas;

FIG. 5 is a diagram schematically illustrating an example of a datastructure stored in a storage area;

FIG. 6 is a diagram schematically illustrating another example of thedata structure stored in the storage area;

FIG. 7 is a diagram schematically illustrating an example of a databasestructure according to a second exemplary embodiment of the invention;

FIG. 8 is a diagram schematically illustrating an example of a databasestructure according to a third exemplary embodiment of the invention;

FIG. 9 is a diagram schematically illustrating an example of a databasestructure according to a fourth exemplary embodiment of the invention;

FIG. 10 is a diagram schematically illustrating an example of a databasestructure according to a fifth exemplary embodiment of the invention;

FIG. 11 is a diagram schematically illustrating an example of a databasestructure according to a sixth exemplary embodiment of the invention;

FIGS. 12A and 12B are diagrams schematically illustrating an example ofa database structure according to a seventh exemplary embodiment of theinvention;

FIG. 13 is a diagram schematically illustrating a portion of a databasestructure according to an eighth exemplary embodiment of the invention;

FIG. 14 is a diagram illustrating the logical connection between entitydata and sub-entity data;

FIG. 15 is a diagram schematically illustrating an example of a databasestructure according to a ninth exemplary embodiment of the invention;

FIG. 16 is a diagram schematically illustrating an example of a databasestructure according to a tenth exemplary embodiment of the invention;and

FIG. 17 is a diagram illustrating the correspondence betweencombinations of a data type and a data format and partition areas.

BEST MODE FOR CARRYING OUT THE INVENTION

Hereinafter, various exemplary embodiments of the invention will bedescribed with reference to the accompanying drawings. In all of thedrawings, components having the same structure or function are denotedby the same reference numerals and a detailed description thereof willnot be arbitrarily omitted with no overlapping description.

(Basic Structure of Database System 10)

FIG. 1 is a functional block diagram illustrating the schematicstructure of a database system 10 according to an exemplary embodimentof the invention. The database system 10 includes a transactionprocessing unit 20, a check point processing unit 30, a defragmentationunit 31, a transaction server 32, and a storage device 40. A database 41and a log file 42 are stored in the storage device 40. The transactionprocessing unit 20 includes a query receiving unit 21, an analysis unit22, a transaction executing unit 23, and a response processing unit 24.

The database system 10 and a plurality of client terminals 501 and 502are connected to a network NW. A general small network (for example, awired or wireless LAN) is given as an example of the network NW, but thenetwork is not particularly limited. The network NW may be a largenetwork, such as the Internet.

Each of the client terminals 501 and 502 has a function of transmittinga query described with a query language (database language), such as astructured query language (SQL) or an XML query language (XQuery), forthe database 41 to the database system 10.

The hardware structure of the database system 10 may be ageneral-purpose structure, and includes, for example, a processor, suchas a central processing unit (CPU), and hardware resources, such as amain memory, a cache memory, a bus for transmitting signals, a timercircuit, an input device (for example, a keyboard), and an output device(for example, a display or a printer). However, the hardware structureof the database system 10 is not particularly limited.

All or some of the structures of the database system 10 may beimplemented by hardware or a computer program (or a program code) thatcauses a processor to perform processes. When the functions of thecomponents 21 to 24, 30, 31, and 32 of the database system 10 areimplemented by the computer program, the processor reads the computerprogram from a storage medium, such as a non-volatile memory, andexecutes the read computer program. The components 21 to 24, 30, 31, 32,and 40 of the database system 10 may be incorporated into one apparatus,or they may be dispersed and incorporated into a plurality ofapparatuses that is operated in cooperation with each other.

FIG. 2 is a flowchart schematically illustrating the procedure of theprocess of the transaction processing unit 20 of the database system 10.In the transaction processing unit 20, the query receiving unit 21receives queries transmitted from the client terminals 501 and 502 (StepS11) and transmits the received queries to the analysis unit 22. Theanalysis unit 22 analyzes the queries (for example, a parsing oroptimizing process) and transmits the analysis result to the transactionexecuting unit 23 (Step S12). The transaction executing unit 23 performsa transaction on the database 41 on the basis of the analysis result(Step S13). The term “transaction” means one work unit including, forexample, a process of searching or updating the database 41, and is aprocess satisfying ACID characteristics, such as atomicity, consistency,isolation, and durability. When the transaction process is normallycompleted (Step S14; YES), the transaction is committed (Step S15).

The transaction executing unit 23 stores the log information (historyinformation) of the transaction as the log file 42 in the storage device40. At the same time, the transaction executing unit 23 stores metadataof the log of the transaction (information about the start or end of thetransaction) in the transaction server 32.

The check point processing unit 30 has a function of periodicallysetting a check point on the basis of the log file 42 and the metadatastored in the transaction server 32. When the transaction does not endnormally due to a failure in the transaction or the system (Step S14 ofFIG. 2; NO), the transaction executing unit 23 performs roll-forward(Step S16). That is, the check point processing unit 30 checks the loginformation during a period Terr from the previously set checkpoint tothe time when a failure occurs with reference to the log file 42 andremoves the log information related to the transaction that has not beencommitted during the period Terr from the log file 42. When there is atransaction that is committed during the period Terr, the transactionexecuting unit 23 reflects the execution result of the transaction tothe database 41 on the basis of the log file 42. Then, the transactionexecuting unit 23 returns the database 41 to the state before thetransaction that is not committed starts to be processed, that is, thetransaction executing unit 23 performs roll-back (Step S17).

The response processing unit 24 receives the execution result of thetransaction from the transaction executing unit 23 and transmits theexecution result to the client terminals 501 and 502 (Step S18).

The database 41 has a structure including an entity data group includinga plurality of entity data and at least one identifier table includingonly a plurality of fixed-length data, which will be described below.The identifier table includes a plurality of data identifiers thatsubstantially uniquely indicates the plurality of entity data as thefixed-length data. In addition, the identifier table includes at leastone tuple that is defined in the row direction and at least oneattribute field that is defined in the column direction and includesdata identifiers, which will be described below.

When selecting specific entity data from the entity data group inresponse to a query request, the transaction executing unit 23 cansearch for a fixed-length data identifier in the identifier tablewithout searching for the entity data group and select the entity dataon the basis of the search result. The transaction executing unit 23 canperform a transaction including a process of searching or updating thedatabase 41 on the basis of the select result.

When the database 41 is repeatedly updated, data is repeatedly stored inor removed from the storage device 40. Therefore, the data group storedin continuous storage areas of the storage device 40 is fragmented(fragmentation), and the cache hit ratio is reduced, which results in alow processing speed. When a plurality of data identifiers is dispersedand stored in a plurality of discontinuous storage areas of the storagedevice 40, the defragmentation unit 31 has a function of reading thesedata identifiers from the storage device 40 and writing the dataidentifiers to the continuous storage areas allocated to the identifiertable.

Next, the structure of the database 41 according to various exemplaryembodiments of the invention will be described.

First Exemplary Embodiment

FIG. 3 is a diagram schematically illustrating an example of a databasestructure according to a first exemplary embodiment of the invention. Asshown in FIG. 3, the database structure includes an entity data groupstored in a storage area DA0 of the storage device 40 and an identifiertable RT0 that is stored in a storage area different from the storagearea DA0.

The identifier table RT0 includes four tuples that are defined in therow direction and four attribute fields TID, Val1, Val2, and Val3 thatare defined in the column direction. In the first exemplary embodiment,for convenience of description, the number of tuples in the identifiertable RT0 is four, but the number of tuples is not limited thereto. Forexample, several tens to millions of tuples may be set. The number ofattribute fields TID, Val1, Val2, and Val3 is not limited to four. Forexample, a “client name”, a “company name”, and a “sex” may be set asthe names (attribute names) of the attribute fields Val1, Val2, andVal3.

Unique tuple identifiers R1, R2, R3, and R4 are allocated to the fourtuples of the identifier table RT0. The attribute field Val1 includesfixed-length data identifiers VR11, VR21, VR31, and VR41 in areascorresponding to four tuples. The attribute field Val2 includesfixed-length data identifiers VR12, VR22, VR32, and VR42 in areascorresponding to four tuples. The attribute field Val3 includesfixed-length data identifiers VR13, VR23, VR33, and VR43 in areascorresponding to four tuples.

The data identifiers VR11 to VR43 have values that substantiallyuniquely indicate the entity data in the storage area DA0. Therefore,the transaction executing unit 23 can search for the data identifiersVR11 to VR43 and access variable-length entity data corresponding to anyone of the data identifiers VR11 to VR43 on the basis of the searchresult. In the specification, the term “substantially uniquely” meanssatisfying uniqueness in the processing of data in the database 41.

For example, when a “client name”, a “company name”, and a “sex” are setas the names (attribute names) of the attribute fields Val1, Val2, andVal3, the data identifiers VR11, VR12, and VR13 may uniquely indicateentity data D11, D12, and D13 of “Yamada Taro”, “N company”, and “male”,respectively, the data identifiers VR21, VR22, and VR23 may uniquelyindicate entity data D21, D22, and D23 of “Sato Hanako”, “F company”,and “female”, respectively, and the data identifiers VR31, VR32, andVR33 may uniquely indicate entity data D31, D32, and D33 of “ItoHajime”, “S company”, and “unknown”, respectively.

The values of the data identifiers VR11 to VR43 can be calculated by aone-way hash function. The hash function outputs a fixed-length bitstring when entity data is input. Therefore, the output value (hashvalue) of the hash function may be used as the values of the dataidentifiers VR11 to VR43. The transaction executing unit 23 can converta search character string into a hash value, retrieve a data identifierhaving a value equal to the hash value from the identifier table RT0,and select entity data corresponding to the retrieved data identifier.In this case, the transaction executing unit 23 searches the identifiertable RT0 including only the fixed-length data group. Therefore, thetransaction executing unit 23 can find out a character string at a highspeed. In particular, it is possible to perform a search process foreach row at a high speed.

As shown in FIG. 4, it is preferable that the data identifiers VR11 toVR41 be stored in continuous storage areas. In this way, access to thedata identifiers VR11 to VR43 is performed at a high speed, and thecache hit ratio is improved. As a result, the search speed is improved.

However, when the database 41 is frequently updated, the dataidentifiers VR11 to VR43 are likely to be dispersed and stored indiscontinuous storage areas. For example, a group of the dataidentifiers VR11 to VR13 and a group of the data identifiers VR21 toVR23 are stored in the storage areas that are separated from each other.In this case, the defragmentation unit 31 reads the data identifiersVR11 to VR43 from the storage area at a predetermined timing and writesthe read data identifiers VR11 to VR43 to continuous areas. In this way,it is possible to prevent a reduction in the search speed.

FIG. 5 is a diagram schematically illustrating an example of the datastructure stored in the storage area DA0. The data structure has aheader area at the head and an allocation management table at the end.An area in which an entity data group is stored is provided between theheader area and the allocation management table.

The header area includes a conversion table indicating thecorrespondence between position data indicating the storage areas of theentity data and data identifiers. Specifically, as shown by symbol F5Bin FIG. 5, the conversion table defines the correspondence between aplurality of data identifiers VR11 to VR43 and position data A11 to A43indicating the storage areas of a plurality of entity data D11 to D43.The position data A11 to A43 may be addresses designating the absolutepositions of the storage areas of the corresponding entity data D11 toD43 or offsets designating the relative positions of the storage areas.The transaction executing unit 23 can search the identifier table RT0and refer to the header area shown by symbol F5A in FIG. 5 to access theentity data D11 to D43. As such, the entity data group and theidentifier table RT0 are logically connected to each other through theheader area. In this way, it is possible to effectively update thedatabase 41 at a high speed, which will be described below.

In the conversion table, the overlap between the data identifiers havingthe same values is excluded (that is, two arbitrary data identifierscertainly have different values in the conversion table). Therefore, theuse of the conversion table makes it possible to store the entity datahaving the same value in the storage area DA0 without any overlaptherebetween. That is, it is possible to compress the entity data groupforming the database 41 and store it in the storage area DA0. Therefore,it is possible to effectively use the storage area DA0.

FIG. 6 is a diagram schematically illustrating another example of thedata structure stored in the storage area DA0. There is no header areaincluding the conversion table in the data structure. As shown by symbolF6B in FIG. 6, a data identifier VR13 for searching having the samevalue as the corresponding data identifier VR13 and a value DL13indicating the bit length of the entity data D13 are added to the entitydata D13, in a manner similar to that for the other entity data. Thetransaction executing unit 23 can search the identifier table RT0 andalso search for data identifiers VR11 to VR43 for searching shown bysymbol F6A in FIG. 6 to access the entity data D11 to D43.

When the database structure according to the first exemplary embodimentis used, the database system 10 has the following effects.

First, it is possible to effectively update the database 41 at a highspeed. That is, the database 41 according to the first exemplaryembodiment includes a plurality of entity data D11 to D43 and aplurality of data identifiers VR11 to VR43 that substantially uniquelyindicates the entity data D11 to D43. For example, during thereplacement of specific entity data D41 in the database 41 with newentity data in response to a query, when there is entity data having thesame value as the new entity data in the storage area D0, it is possibleto update the database 41 only by replacing the data identifier VR41 inthe identifier table RT0 with a new data identifier without actuallyrewriting the entity data D41 in the storage area D0.

During the addition (insertion) of a record to the entity data group inresponse to a query, when there is entity data having the same value asentity data to be included in the record in the storage area D0, it ispossible to update the database 41 only by adding a data identifiercorresponding to the record to the identifier table RT0. When the entitydata D41 is removed from the entity data group in response to a query,it is possible to update the database 41 only by removing the dataidentifier VR41 from the identifier table RT0, without directly removingthe entity data D41 from the storage area D0.

As such, it is possible to ensure a high real-time performance in theprocessing of the database in response to an update query, such asreplacement, addition, or removal. Even when the database 41 isfrequently updated, it is possible to effectively update the database ata high speed.

Second, it is possible to improve the portability of the database. Thatis, since the data identifiers VR11 to VR43 substantially uniquelyindicate the entity data D11 to D43, the dependency of the dataidentifiers VR11 to VR43 on the hardware structure is low. Therefore, itis possible to easily port the database according to the first exemplaryembodiment to other systems.

Third, it is possible to improve the dispersibility of the database 41.As described above, the storage area allocated to the identifier tableRT0 is different from the storage area DAD allocated to the entity datagroup. That is, the identifier table RT0 is completely separated fromthe entity data group. Therefore, it is easy to arrange the identifiertable RT0 and the entity data group so as to be dispersed. For example,it is possible to disperse the identifier table RT0 and the entity datagroup in two computer systems that are connected to through a computernetwork, such as a LAN.

Fourth, it is possible to prevent a reduction in the speed of access tothe database 41. As described above, even when the data identifiers VR11to VR43 are dispersed and stored in discontinuous storage areas(fragmentation), the defragmentation unit 31 can rewrite the dataidentifiers VR11 to VR43 to continuous storage areas. Therefore, it ispossible to prevent a reduction in the speed of access to the database41.

Second Exemplary Embodiment

FIG. 7 is a diagram schematically illustrating an example of a databasestructure according to a second exemplary embodiment of the invention.As shown in FIG. 7, the database structure includes an entity data groupthat is stored in a storage area DA1 of a storage device 40, and a linktable LT1 and first and second column tables (identifier tables) CT11and CT12 that are stored in a storage area different from the storagearea DA1. The reference table RT0 shown in FIG. 3 includes a pluralityof attribute fields (columns) and each column includes data identifiers.In this exemplary embodiment, each of the column tables CT11 and CT12has a data structure corresponding to each column of the reference tableRT0 shown in FIG. 3. Each of the data structure of the column table CT11and the data structure of the column table CT12 may be stored in astorage area in which the addresses are not continuous or a storage areain which the addresses are continuous.

The first column table CT11 includes a plurality of tuples defined inthe row direction and one attribute field Val defined in the columndirection. The attribute field Val includes fixed-length dataidentifiers VR12, VR12, VR11, and VR11 in areas corresponding to fourtuples. The second column table CT12 includes a plurality of tuplesdefined in the row direction and an attribute field Val defined in thecolumn direction. The attribute field Val includes fixed-length dataidentifiers VR23, VR24, VR22, and VR21 in areas corresponding to fourtuples. For example, a “client name” may be set as the name (attributename) of the attribute field Val of the column table CT11 and a “sex”may be set as the name of the attribute field Val of the column tableCT12. In this case, the data identifiers VR12 and VR11 uniquely indicateentity data D12 and D11 of “Yamada Taro” and “Sato Hanako”, and the dataidentifiers VR21 to VR24 uniquely indicate entity data D21 to D24 of“male” and “female”.

The data identifiers VR11 to VR24 have values that substantiallyuniquely indicate the entity data D11 to D24 in the storage area DA1.Therefore, the transaction executing unit 23 can search for the dataidentifiers VR11 to VR24 and access variable-length entity data on thebasis of the search result. The storage area DA1 may have the sameconversion table as that shown in FIG. 5 or the same data identifier forsearching as that shown in FIG. 6.

It is preferable that data identifiers be stored in continuous areas ineach of the column tables CT11 and CT12. In this way, the speed ofaccess to the data identifier increases and the cache hit ratio alsoincreases. Therefore, the search speed is improved. Even when thedatabase 41 is frequently updated, the defragmentation unit 31 reads onegroup of data identifiers from the storage area at a predeterminedtiming and writes the read data identifiers to continuous areas. In thisway, it is possible to prevent a reduction in the search speed.

The link table LT1 has a structure that connects the tuples between thefirst column table CT11 and the second column table CT12. That is, thelink table LT1 includes a plurality of tuples defined in the rowdirection and two attribute fields TID and OST defined in the columndirection. The attribute field TID includes tuple identifiers R1, R2,R3, and R4 that uniquely indicate the tuples. The attribute field OSTincludes offsets Vo1, Vo2, Vo3, and Vo4 that designate the relativepositions of the storage areas of the tuples in the column tables CT11and CT12. For example, the offset Vo1 is added to a predeterminedreference address A0, thereby obtaining an effective address Vo1+A0designating the absolute position of the storage area of the dataidentifier VR12.

Similar to the first exemplary embodiment, the values of the dataidentifiers VR11 to VR24 included in each of the first and second columntables CT11 and CT12 may be calculated by a one-way hash function. Thetransaction executing unit 23 can convert a search character string intoa hash value, retrieve a data identifier having a value equal to thehash value from the column tables CT11 and CT12, and select entity datacorresponding to the retrieved data identifier. In this case, thetransaction executing unit 23 searches the column tables CT11 and CT12including only a fixed-length data group. Therefore, the transactionexecuting unit 23 can find out a character string at a high speed.

The database according to the second exemplary embodiment may beconsidered as a database in which two columns of tabular data aredivided into the first column table CT11, the second column table CT12,and the entity data group. Therefore, it is possible to perform a searchprocess for each column at a high speed.

In the second exemplary embodiment, the number of attribute fields Valin each of the column tables CT11 and CT12 is one, but the number ofattribute fields Val is not limited to one. For example, the number ofattribute fields in each of the column tables CT11 and CT12 may be setto two or more. In addition, the number of column tables CT11 and CT12is not limited to two, but it may be three or more.

When the database structure according to the second exemplary embodimentis used, the database system 10 has the following effects.

First, it is possible to effectively update the database 41 at a highspeed. That is, the database according to the second exemplaryembodiment includes a plurality of entity data and a plurality of dataidentifiers VR11 to VR24 that substantially uniquely indicates theentity data. Therefore, similar to the first exemplary embodiment, it ispossible to effectively perform the database process in response to anupdate query, such as update, addition, or removal, and thus ensure ahigh real time performance. Therefore, even when the database 41 isfrequently updated, it is possible to effectively update the database ata high speed.

Second, it is possible to improve the dispersibility of the database.The column tables CT11 and CT12 are completely separated from the entitydata group. Therefore, similar to the first exemplary embodiment, it iseasy to arrange the column tables CT11 and CT12 and the entity datagroup so as to be dispersed.

Third, it is possible to flexibly determine the logical connection ofthe tuples between the column tables CT11 and CT12. For example, asshown in FIG. 7, it is possible to logically connect the tuple storedafter an effective address A0+Vo3 of the column table CT11 and the tuplestored after an effective address A1+Vo3 of the column table CT12 usingthe offset Vo3 corresponding to the tuple identifier R3. At the sametime, it is possible to logically connect the tuple stored after aneffective address A0+Vo4 of the column table CT11 and the tuple storedafter an effective address A1+Vo4 of the column table CT12 using theoffset Vo4 corresponding to the tuple identifier R4.

Fourth, the column tables CT11 and CT12 are logically connected to eachother by only one attribute field OST of the link table LT1. Therefore,it is possible to significantly reduce the amount of data in the linktable LT1.

Third Exemplary Embodiment

FIG. 8 is a diagram schematically illustrating an example of a databasestructure according to a third exemplary embodiment of the invention. Asshown in FIG. 8, the database structure includes an entity data groupthat is stored in a storage area DA1 of a storage device 40, and a linktable LT2 and first and second column tables (identifier tables) CT11and CT12 that are stored in a storage area different from the storagearea DA1.

The database structure according to the third exemplary embodiment isthe same as that according to the second exemplary embodiment except forthe link table LT2.

The link table LT2 has a structure that connects the tuples between thefirst column table CT11 and the second column table CT12. That is, thelink table LT2 includes a plurality of tuples defined in the rowdirection and first to third attribute fields TID, PT1, and PT2 definedin the column direction. The first attribute field TID includes tupleidentifiers R1, R2, R3, and R4 that uniquely indicate the tuples. Thesecond attribute field PT1 includes pointers Vp11, Vp12, Vp13, and Vp14that designate the addresses allocated to the storage areas of thetuples in the column table CT11. The third attribute field PT2 includespointers Vp21, Vp22, Vp23, and Vp24 that designate the addressesallocated to the storage areas of the tuples in the column table CT12.

The transaction executing unit 23 can search for data identifiers VR11to VR24 in the first and second column tables CT11 and CT12 through thelink table LT2 and access entity data on the basis of the search result.The database according to the third exemplary embodiment can beconsidered as a database in which two columns of tabular data aredivided into the first column table CT11, the second column table CT12,and the entity data group. Therefore, it is possible to perform a searchprocess for each column at a high speed.

In the third exemplary embodiment, the number of column tables CT11 andCT12 is not limited to two, but it may be three or more. In this case,the link table LT2 also includes attribute fields corresponding to aplurality of column tables.

When the database structure according to the third exemplary embodimentis used, the database system 10 has the following effects. Similar tothe second exemplary embodiment, first, it is possible to effectivelyupdate the database 41 at a high speed. Second, it is possible toimprove the dispersibility of the database.

Third, it is possible to flexibly determine the logical connection ofthe tuples between the column tables CT11 and CT12. That is, since thelink table LT2 has the attribute fields including pointers for eachcolumn table, the database structure according to the third exemplaryembodiment can more flexibly determine the connection of the tuplesbetween the column tables CT11 and CT12 than the database structureaccording to the second exemplary embodiment. For example, it ispossible to change the logical positions of the data identifiers VR23,VR24, VR22, VR21, . . . in the column table CT12 in the link table LT2only by changing any one of the values of the pointers Vp21, Vp22, Vp23,and Vp24 in the attribute field PT2 of the link table LT2. In this case,the other column table CT11 is not affected by the change of the logicalpositions.

In the example shown in FIG. 8, the column table CT11 has the duplicateddata identifiers VR12 and VR12. However, it is possible to remove theduplication by changing the pointer in the attribute field PT1 of thelink table LT2 (for example, by changing the pointer Vp12 to the pointerVp11). Therefore, it is possible to compress the amount of data.

Fourth, since the first column table CT11 is logically separated fromthe second column table CT12, the transaction executing unit 23 cansimultaneously perform a search process for the first column table CT11and a search process for the second column table CT12 in response to aquery designating the search conditions. Therefore, it is possible toimprove the search speed.

Fourth Exemplary Embodiment

FIG. 9 is a diagram schematically illustrating an example of a databasestructure according to a fourth exemplary embodiment of the invention.As shown in FIG. 9, the database structure includes an entity data groupthat is stored in a storage area DA2 of a storage device 40, and a linktable LT3 and first and second column tables (identifier tables) CT31and CT32 that are stored in a storage area different from the storagearea DA2. As described above, the reference table RT0 shown in FIG. 3has a plurality of attribute fields (columns), and each column includesdata identifiers. In this exemplary embodiment, each of the columntables CT31 and CT32 has a data structure corresponding to each columnof the reference table RT0 shown in FIG. 3. Each of the data structureof the column table CT31 and the data structure of the column table CT32may be formed in a storage area in which the addresses are notcontinuous or a storage area in which the addresses are continuous.

The first column table CT31 includes four tuples defined in the rowdirection and two attribute fields Col1 and Val defined in the columndirection. The attribute field Col1 includes fixed-length tupleidentifiers CRV1, CRV2, CRV3, and CRV4 in areas corresponding to thefour tuples. The attribute field Val includes fixed-length dataidentifiers VR12, VR12, VR11, and VR11 in areas corresponding to thefour tuples. Each of the tuple identifiers CRV1, CRV2, CRV3, and CRV4 ofthe first column table CT31 has a value that uniquely indicates thetuples of the first column table CT31.

The second column table CT32 includes four tuples defined in the rowdirection and two attribute fields Col2 and Val defined in the columndirection. The attribute field Colt includes fixed-length tupleidentifiers CRV1, CRV2, CRV3, and CRV4 in areas corresponding to thefour tuples. The attribute field Val includes fixed-length dataidentifiers VR23, VR24, VR21, and VR22 in areas corresponding to thefour tuples. Each of the tuple identifiers CRV1, CRV2, CRV3, and CRV4 ofthe second column table CT32 has a value that uniquely indicates thetuples of the second column table CT32.

The data identifiers VR11 to VR24 have values that substantiallyuniquely indicate the entity data D11 to D24 in the storage area DA2.Therefore, the transaction executing unit 23 can search for the dataidentifiers VR11 to VR24 and access variable-length entity data on thebasis of the search result. The storage area DA2 may have the sameconversion table as that shown in FIG. 5 or the same data identifier forsearching as that shown in FIG. 6.

It is preferable that data identifiers be stored in continuous areas ineach of the column tables CT31 and CT32. In this way, the speed ofaccess to the data identifier increases and the cache hit ratio alsoincreases. Therefore, the search speed is improved. Even when thedatabase 41 is frequently updated, the defragmentation unit 31 reads onegroup of data identifiers from the storage area at a predeterminedtiming and writes the read data identifiers to continuous areas. In thisway, it is possible to prevent a reduction in the search speed.

The link table LT3 has a structure that connects the tuples between thefirst column table CT31 and the second column table CT32. That is, thelink table LT3 includes four tuples defined in the row direction and twoattribute fields TID and ColRef defined in the column direction. Theattribute field TID includes tuple identifiers R1, R2, R3, and R4 thatuniquely indicate the tuples. The attribute field ColRef includesexternal tuple identifiers CRV1, CRV2, CRV3, and CRV4 that substantiallyuniquely indicate the tuples (external tuples) of the column tables CT31and CT32. The external tuple identifiers CRV1, CRV2, CRV3, and CRV4 havethe same values as the tuple identifiers CRV1, CRV2, CRV3, and CRV4 ofthe first column table CT31 and the second column table CT32, but theinvention is not limited thereto. The tuple identifiers may have valuescorresponding to the external tuple identifiers CRV1, CRV2, CRV3, andCRV4.

Similar to the first exemplary embodiment, the values of the dataidentifiers VR11 to VR24 included in each of the first and second columntables CT31 and CT32 may be calculated by a one-way hash function. Thetransaction executing unit 23 can convert a search character string intoa hash value, retrieve a data identifier having a value equal to thehash value from the column tables CT31 and CT32, and select entity datacorresponding to the retrieved data identifier. In this case, thetransaction executing unit 23 searches the column tables CT31 and CT32including only a fixed-length data group. Therefore, the transactionexecuting unit 23 can find out a character string at a high speed.

The database according to the fourth exemplary embodiment may beconsidered as a database in which two columns of tabular data aredivided into the first column table CT31, the second column table CT32,and the entity data group. Therefore, it is possible to perform a searchprocess for each column at a high speed.

In this exemplary embodiment, the number of attribute fields in each ofthe column tables. CT31 and CT32 is two, but is not limited to two. Forexample, the number of attribute fields in each of the column tablesCT31 and CT32 may be set to three or more. In addition, the number ofcolumn tables CT31 and CT32 is not limited to two, but it may be threeor more.

When the database structure according to the fourth exemplary embodimentis used, the database system 10 has the following effects.

First, similar to the second exemplary embodiment, it is possible toeffectively update the database 41 at a high speed. Second, it ispossible to improve the dispersibility of the database. Third, it ispossible to flexibly determine the logical connection of the tuplesbetween the column tables CT31 and CT32.

Fourth, it is possible to improve the portability of the database. Thatis, since the data identifiers VR11 to VR24 substantially uniquelyindicate the entity data D11 to D24, the dependency of the dataidentifiers VR11 to VR24 on the hardware structure is low, similar tothe tuple identifiers CRV1 to CRV4 and the external tuple identifiersCRV1 to CRV4. Therefore, it is possible to easily port the databaseaccording to the fourth exemplary embodiment to other systems.

Fifth Exemplary Embodiment

FIG. 10 is a diagram schematically illustrating an example of a databasestructure according to a fifth exemplary embodiment of the invention. Asshown in FIG. 10, the database structure includes an entity data groupthat is stored in a storage area DA3 of a storage device 40, and areference table RT1 and first to third intermediate identifier tablesIT41, IT42, and IT43 that are stored in a storage area different fromthe storage area DA3. The intermediate identifier tables IT41, IT42, andIT43 may be data structures that are stored in a storage area differentfrom the storage area DA3. In this case, the data structure of each ofthe intermediate identifier tables IT41, IT42, and IT43 may be formed ina storage area in which the addresses are not continuous or a storagearea in which the addresses are continuous.

Alternatively, the intermediate identifier tables IT41, IT42, and IT43may be data structures stored in the storage area DA3. In this case, thestorage area DA3 may have the same header area as that shown in FIG. 5and the data structure of each of the intermediate identifier tablesIT41, IT42, and IT43 may be stored in the header area together with aconversion table.

The first intermediate identifier table IT41 includes two tuples definedin the row direction and two attribute fields Col1 and Val defined inthe column direction. The attribute field Col1 includes fixed-lengthtuple identifiers CRV11 and CRV12 in areas corresponding to the twotuples. The attribute field Val includes fixed-length data identifiersVR11 and VR12 in areas corresponding to the two tuples.

The second intermediate identifier table IT42 includes four tuplesdefined in the row direction and two attribute fields Col2 and Valdefined in the column direction. The attribute field Col2 includesfixed-length tuple identifiers CRV21, CRV22, CRV23, and CRV24 in areascorresponding to the tour tuples. The attribute field Val of the secondintermediate identifier table IT42 includes fixed-length dataidentifiers VR21, VR22, VR23, and VR24 in areas corresponding to thefour tuples.

The third intermediate identifier table IT43 includes three tuplesdefined in the row direction and two attribute fields Col3 and Valdefined in the column direction. The attribute field Col3 includesfixed-length tuple identifiers CRV31, CRV32, and CRV33 in areascorresponding to the three tuples. The attribute field Val of the thirdintermediate identifier table IT43 includes fixed-length dataidentifiers VR31, VR32, and VR33 in areas corresponding to the threetuples.

The first to third intermediate identifier tables IT41, IT42, and IT43have data identifiers VR11 to VR33 that substantially uniquely indicateentity data D11 to D33 in the storage area DA3.

The reference table RT1 has reference identifiers CRV11 to CRV33 thatsubstantially uniquely indicate the data identifiers VR11 to VR33 in thefirst to third intermediate identifier tables IT41 to IT43,respectively. In this exemplary embodiment, the reference identifiersCRV11 to CRV33 have the same shape as the tuple identifiers CRV11 toCRV33 in the first to third intermediate identifier tables IT41 to IT43.In this way, the reference identifiers CRV11 to CRV33 substantiallyuniquely indicate the data identifiers VR11 to VR33, respectively. Forexample, the values of the reference identifiers CRV11 to CRV33 may bethe values of the hash function when the data identifiers VR11 to VR33are input.

As shown in FIG. 10, the reference table RT1 includes four tuplesdefined in the row direction and first to fourth attribute fields TID,Col1Ref, Col2Ref, and Col3Ref defined in the column direction. The firstattribute field TID includes tuple identifiers R1, R2, R3, and R4 thatuniquely indicate the tuples. The second attribute field Col1Refincludes a set of reference identifiers CRV12, CRV12, CRV11, and CRV11that substantially uniquely indicate the data identifiers VR11 and VR12of the first intermediate identifier table IT41. The third attributefield Col2Ref includes a set of reference identifiers CRV21, CRV22,CRV23, and CRV24 that substantially uniquely indicate the dataidentifiers VR21, VR22, VR23, and VR24 of the second intermediateidentifier table IT42. The fourth attribute field Col3Ref includes a setof reference identifiers CRV31, CRV32, and CRV33 that substantiallyuniquely indicate the data identifiers VR31, VR32, and VR33 of the thirdintermediate identifier table IT43.

For example, a “location”, a “company name”, and an “age group” can beset as the names (attribute names) of the attribute fields Col1Ref,Col2Ref, and Col3Ref in the reference table RT1. The data identifiersCRV12, CRV23, and CRV32 in the tuple (record) corresponding to the tupleidentifier R1 uniquely indicate the data identifiers VR12, VR23, andVR32, respectively, and the data identifiers VR12, VR23, and VR32uniquely indicate the entity data D12, D23, and D32 of “Shinagawa”, “Ncompany”, and “twenties”, respectively. Similarly, the data identifiersCRV12, CRV24, and CRV33 in the tuple corresponding to the tupleidentifier R2 uniquely indicate the data identifiers VR12, VR24, andVR33, respectively, and the data identifiers VR12, VR24, and VR33uniquely indicate the entity data D12, D24, and D33 of “Tamachi”, “Acompany”, and “thirties”, respectively. The data identifiers CRV11,CRV21, and CRV33 in the tuple corresponding to the tuple identifier R3uniquely indicate the data identifiers VR11, VR21, and VR33,respectively, and the data identifiers VR11, VR21, and VR33 uniquelyindicate the entity data D11, D21, and D33 of “Tamachi”, “A company”,and “thirties”, respectively. The data identifiers CRV11, CRV22, andCRV31 in the tuple corresponding to the tuple identifier R4 uniquelyindicate the data identifiers VR11, VR22, and VR31, respectively, andthe data identifiers VR11, VR22, and VR31 uniquely indicate the entitydata D11, D22, and D31 of “Tamachi”, “S company”, and “forties”,respectively.

Similar to the first exemplary embodiment, the values of the dataidentifiers VR11 to VR33 included in each of the first to thirdintermediate identifier tables IT41, IT42, and IT43 may be calculated byusing a one-way hash function. The values of the reference identifiersCRV11 to CRV33 can be calculated by using a hash function. For example,the output values of the hash function when the values of the dataidentifiers VR11 to VR33 are input may be used as the values of thereference identifiers CRV11 to CRV33. The transaction executing unit 23can convert a search character string into a hash value, retrieve areference identifier having a value equal to the hash value from thereference table RT1, and access entity data corresponding to theretrieved reference identifier. In this case, the transaction executingunit 23 searches the reference table RT1 including only a fixed-lengthdata group. Therefore, the transaction executing unit 23 can find out acharacter string at a high speed.

The transaction executing unit 23 can search for the referenceidentifiers CRV11 to CRV33 and the data identifiers VR11 to VR33 andaccess variable-length entity data on the basis of the search result.The storage area DA3 may have the same conversion table as that shown inFIG. 5 or the same data identifier for searching as that shown in FIG.6.

Each of the first to third intermediate identifier tables IT41, IT42,and IT43 has a data structure excluding redundancy, because the dataidentifiers having the same value are excluded. In this way, it ispossible to effectively use the storage area.

It is preferable that the data identifiers be stored in continuous areasin each of the first to third intermediate identifier tables IT41 toIT43. It is preferable that the reference identifiers CRV11 to CRV33 bestored in continuous areas in the reference table RT1. In this way, thespeed of access to the data identifiers and the reference identifiersincreases and the cache hit ratio also increases. As a result, thesearch speed is improved.

Even when the database 41 is frequently updated, the defragmentationunit 31 reads one group of data identifiers or one group of referenceidentifiers from the storage area at a predetermined timing and writesthe read data identifiers or reference identifiers to continuous areas.In this way, it is possible to prevent a reduction in the search speed.

The defragmentation unit 31 has a function of rearranging a plurality ofdata identifiers in the attribute field Val in increasing order ordecreasing order of the values of the reference identifierscorresponding to the data identifier in each of the first to thirdintermediate identifier tables IT41 to IT43. In this way, it is possibleto effectively perform a search process.

When the database structure according to the fifth exemplary embodimentis used, the database system 10 has the following effects.

First, it is possible to effectively update the database 41 at a highspeed. That is, the database according to the fifth exemplary embodimentincludes a plurality of entity data and a plurality of data identifiersVR11 to VR33 that substantially uniquely indicates the entity data.Therefore, when the record is updated, added, or removed, the update ofthe reference table RT1 as well as the intermediate identifier tablesIT41 to IT43 is minimized. Therefore, even when the database 41 isfrequently updated, the update can be effectively performed at a highspeed.

For example, when a new record is added (inserted), the transactionexecuting unit 23 converts the record into a reference record includingthe reference identifiers and newly adds the reference record to thereference table RT1 so as to be associated with the tuple identifier R5.Then, the transaction executing unit 23 determines whether the referenceidentifier (new reference identifier) in the newly added referencerecord is in the existing reference record corresponding to the tupleidentifiers R1 to R4. When it is determined that the new referenceidentifier is in the existing reference record, the transactionexecuting unit 23 ends the update process for the database 41. On theother hand, when it is determined that the new reference identifier isnot in the existing reference record, the transaction executing unit 23adds a data identifier corresponding to the new reference identifier toany one of the intermediate identifier tables IT41 to IT43 and addsentity data corresponding to the new reference identifier to the storagearea DA3.

When the new reference identifier is in the existing reference record,only the reference table RT1 is updated. Therefore, it is possible tocomplete the update of the database 41 in a short time. For example,when the reference record to be newly added includes a new referenceidentifier CRV13 that does not exist in the reference table RT1, a tupleidentifier CRV13 and a data identifier VR13 are added to theintermediate identifier table IT41. At the same time, entity data D13 isadded to the storage area DA3. On the other hand, when the referencerecord to be newly added includes only a new reference identifier CRV11that has previously existed in the reference table RT1, the intermediateidentifier tables IT41 to IT43 and the entity data group are notupdated.

Second, it is possible to improve the dispersibility of the database.The intermediate identifier tables IT41 to IT43 are completely separatedfrom the entity data group. Therefore, similar to the first exemplaryembodiment, it is easy to arrange the intermediate identifier tablesIT41 to IT43 and the entity data group so as to be dispersed. Inaddition, it is easy to arrange the intermediate identifier tables IT41to IT43 and the reference table RT1 so as to be dispersed.

Sixth Exemplary Embodiment

FIG. 11 is a diagram schematically illustrating an example of a databasestructure according to a sixth exemplary embodiment of the invention. Asshown in FIG. 11, the database structure includes an entity data groupthat is stored in a storage area DA4 of a storage device 40, and areference table RT1 and first to third intermediate identifier tablesIT41, IT42, and IT43 that are stored in a storage area different fromthe storage area DA4.

In this exemplary embodiment, the storage area DA4 allocated to theentity data group is divided into a plurality of partition areas PA1,PA2, and PA3. The partition areas PA1, PA2, and PA3 are allocated so asto store different types of entity data in the entity data group. Forexample, only integer-type entity data is stored in the partition areaPA1. Only character string-type entity data is stored in the partitionarea PA2. Only date-type entity data is stored in the partition areaPA3. In this exemplary embodiment, the number of partition areas PA1,PA2, and PA3 is three, but is not limited thereto.

As such, when the entity data is stored in the partition areascorresponding to the types of entity data, it is possible to effectivelyuse the storage area DA4.

Seventh Exemplary Embodiment

FIGS. 12A and 12B are diagrams schematically illustrating an example ofa database structure according to a seventh exemplary embodiment of theinvention. As shown in FIG. 12A, the database structure includes anentity data group that is stored in a storage area DA5 of a storagedevice 40, and a reference table RT1 and first to third intermediateidentifier tables IT41, IT42, and IT43 that are stored in a storage areadifferent from the storage area DA5.

In this exemplary embodiment, similar to the fifth exemplary embodiment,the first to third intermediate identifier tables IT41, IT42, and IT43include data identifiers VR11 to VR33 that substantially uniquelyindicate entity data D11 to D33 in the storage area DA5, respectively.However, the entity data D11 to D33 is included in combination data KD11to KD33, respectively. In each of the first to third intermediateidentifier tables IT41, IT42, and IT43, the data identifiers having thesame value are excluded.

FIG. 12B is a diagram schematically illustrating the structure of thecombination data KD12. The combination data KD12 includes entity dataD12, first sub-entity data T12 a, and second sub-entity data T12 b. Theentity data D12, the first sub-entity data T12 a, and the secondsub-entity data T12 b are stored in continuous storage areas.

The first sub-entity data T12 a and the second sub-entity data T12 bhave content related to the entity data D12. For example, when theentity data D12 is binary data, the first sub-entity data T12 a may betext data indicating the content of the binary data. When the entitydata D12 indicates the content of character string-type data “11”, thefirst sub-entity data T12 a may indicate the content of integer-typedata “11”, and the second sub-entity data T12 b may indicate the contentof floating-point-type data “11.00”. Alternatively, when the entity dataD12 indicates the content of Japanese text, the first sub-entity dataT12 a may indicate the content of English text and the second sub-entitydata T12 b may indicate the content of Russian text.

When selecting the entity data D12 in response to a query request bysearching the reference table RT1 and the intermediate identifier tablesIT41 to IT43, the transaction executing unit 23 can read the entity dataD12 and the sub-entity data T12 a and T12 b. Alternatively, thetransaction executing unit 23 may read the sub-entity data T12 a or T12b instead of the entity data D12.

When the database structure according to the seventh exemplaryembodiment is used, the transaction executing unit 23 successfullyevades converting the entity data D12 read from the database 41 into thefirst sub-entity data T12 a or the second sub-entity data T12 b inresponse to a query request. Therefore, it is possible to improve aresponse speed to the query.

Eighth Exemplary Embodiment

FIG. 13 is a diagram schematically illustrating a portion of a databasestructure according to an eighth exemplary embodiment of the invention.As shown in FIG. 13, the database structure includes an entity datagroup that is stored in a storage area DA6 of a storage device 40, and areference table RT1 (not shown) and first to third intermediateidentifier tables IT41, IT42, and IT43 (not shown) that are stored in astorage area different from the storage area DA6.

In this exemplary embodiment, combination data MD11 to MD33 includingentity data D11 to D33 respectively corresponding to data identifiersVR11 to VR33 of the intermediate identifier tables IT41, IT42, and IT43are stored in a partition area QA1 of the storage area DA6. Combinationdata MT11 a to MT33 a including sub-entity data T11 a to T33 a havingcontent related to the entity data D11 to D33 are stored in a partitionarea QA2 of the storage area DA6. Combination data MT11 b to MT33 bincluding sub-entity data T11 b to T33 b having content related to theentity data D11 to D33 are stored in a partition area QA3 of the storagearea DA6.

As shown in FIG. 14, position data P31 indicating the position of thestorage area of the sub-entity data T31 a having content related to theentity data D31 is added to the entity data D31 forming the combinationdata MD31. In addition, position data P31 a indicating the position ofthe storage area of the sub-entity data T31 b having content related tothe entity data D31 is added to the sub-entity data T31 a.

As such, in the database structure according to this exemplaryembodiment, the entity data D31 is logically connected to the sub-entitydata T31 a and T31 b. The position data P31 and P31 a may be addressesdesignating the absolute position of the storage areas, offsetsdesignating the relative positions of the storage areas, or pointersdesignating the addresses allocated to the storage areas, similar toother entity data.

When selecting the entity data D31 in response to a query request bysearching the reference table RT1 and the intermediate identifier tablesIT41 to IT43, the transaction executing unit 23 can read the entity dataD31 and the sub-entity data T31 a and T31 b. Alternatively, thetransaction executing unit 23 may read the sub-entity data T31 a or T31b instead of the entity data D31.

Therefore, when the database structure according to the eighth exemplaryembodiment is used, the transaction executing unit 23 does not convertthe entity data D31 read from the database 41 into the first sub-entitydata T31 a or the second sub-entity data T31 b in response to a queryrequest. Therefore, it is possible to improve a response speed to thequery.

Ninth Exemplary Embodiment

FIG. 15 is a diagram schematically illustrating an example of a databasestructure according to a ninth exemplary embodiment of the invention. Asshown in FIG. 15, the database structure includes an entity data groupthat is stored in a storage area DA7 of a storage device 40, and areference table RT1 and first to third intermediate identifier tablesIT41 a, IT42 a, and IT43 a that are stored in a storage area differentfrom the storage area DA7.

Entity data D11 to D33 are stored in a partition area RA1 of the storagearea DA7. Sub-entity data T11 a to T33 a having content related to theentity data D11 to D33 are stored in a partition area RA2 of the storagearea DA7.

The intermediate identifier table IT41 a includes an attribute field TRin addition to the attribute fields Col1 and Val of the intermediateidentifier table IT41 (FIG. 10). The attribute field TR includessub-data identifiers VT11 and VT12 that are in one-to-one correspondencewith the data identifiers VR11 and VR12 in the attribute field Val andsubstantially uniquely indicate the sub-entity data T11 a and T12 a,respectively. Similarly, the intermediate identifier table IT42 aincludes an attribute field TR in addition to the attribute fields Coltand Val of the intermediate identifier table IT42 (FIG. 10). Theattribute field TR includes sub-data identifiers VT21 to VT24 that arein one-to-one correspondence with the data identifiers VR21 to VR24 inthe attribute field Val and substantially uniquely indicate thesub-entity data T21 a to T24 a, respectively. The intermediateidentifier table IT43 a includes an attribute field TR in addition tothe attribute fields Col3 and Val of the intermediate identifier tableIT43 (FIG. 10). The attribute field TR includes sub-data identifiersVT31 to VT33 that are in one-to-one correspondence with the dataidentifiers VR31 to VR33 in the attribute field Val and substantiallyuniquely indicate the sub-entity data T31 a to T33 a, respectively. Thevalue of the sub-data identifiers VT11 to VT33 may be calculated by ahash function that outputs a fixed-length bit string when sub-entitydata is input.

When selecting, for example, entity data D12 from the entity data groupin response to a query request by searching the reference table RT1 andthe intermediate identifier tables IT41 a to IT43 a, the transactionexecuting unit 23 can read the sub-entity data T12 a having contentrelated to the selected entity data D12 using the sub-data identifierVT12. Alternatively, the transaction executing unit 23 may read thesub-entity data T12 a instead of the entity data D12.

Therefore, when the database structure according to the ninth exemplaryembodiment is used, the transaction executing unit 23 successfullyevades converting the entity data D12 read from the database 41 into thesub-entity data T12 a in response to a query request. Therefore, it ispossible to improve a response speed to the query.

Tenth Exemplary Embodiment

FIG. 16 is a diagram schematically illustrating an example of a databasestructure according to a tenth exemplary embodiment of the invention. Asshown in FIG. 16, the database structure includes an entity data groupthat is stored in a storage area DA8 of a storage device 40, and areference table RT1 and first to third intermediate identifier tablesIT41, IT42, and IT43 that are stored in a storage area different fromthe storage area DA8.

In this exemplary embodiment, the storage area DA8 allocated to theentity data group is divided into a plurality of partition areas PAa,PAb, PAc, and PAd. The partition areas PAa, PAb, PAc, and PAd areallocated as areas in which entity data having different combinations ofa data type and a data format in the entity data group are stored.Examples of the data type include an integer type, a characterstring-type, and a date type. Examples of the data format include aJapanese format and an English format. However, the invention is notlimited thereto.

FIG. 17 is a diagram (conversion table) illustrating the correspondencebetween the partition areas and combinations of the data type and thedata format. The database structure according to this exemplaryembodiment may include the conversion table shown in FIG. 17, or theconversion table shown in FIG. 17 may be stored in a storage areadifferent from the storage area allocated to the database 41. As shownin the conversion table of FIG. 17, only the entity data group having acombination of data format 1 and data type 1 is stored in the partitionarea PAa, and only the sub-entity data group having a combination ofdata format 2 and data type 1 is stored in the partition area PAb. Inaddition, only the sub-entity data group having a combination of dataformat 1 and data type 2 is stored in the partition area PAc, and onlythe sub-entity data group having a combination of data format 2 and datatype 2 is stored in the partition area PAd.

The transaction executing unit 23 can select one storage area from thepartition areas PAa to PAd with reference to the conversion table shownin FIG. 17 in response to a query request and read entity data orsub-entity data from the selected storage area.

Therefore, when the database structure according to the tenth exemplaryembodiment is used, the transaction executing unit 23 successfullyevades converting the entity data read from the database 41 into thesub-entity data in response to a query request. Therefore, it ispossible to improve a response speed to the query.

The exemplary embodiments of the invention have been described abovewith reference to the drawings, but the invention is not limited to theabove-described exemplary embodiments. It will be understood by thoseskilled in the art that the structure or details of the invention can bechanged in various ways within the scope of the invention.

The above-described exemplary embodiments of the invention areillustrative, and the invention can adopt various structures other thanthe above-mentioned structures. For example, in the above-describedexemplary embodiments, a process suitable to perform a transaction onthe database 41 is performed, but the invention is not limited thereto.As described above, the transaction is a process satisfying the ACIDcharacteristics, but the database structure according to the inventioncan also be applied to data processing that does not satisfy all of theACID characteristics.

In the above-described exemplary embodiments, the query receiving unit21 receives a query described with a query language, and the analysisunit 22 analyzes the query. However, the invention is not limitedthereto. For example, the query may not be described with the querylanguage, but may simply include a value for calling an applicationprogramming interface (API) function for a database.

The structure of the storage area DA4, DA5, DA6, DA7, or DA8 accordingto the sixth to tenth exemplary embodiments may be applied instead ofthe storage area DA0, DA1, DA2, or DA3 according to the first to fifthexemplary embodiments.

The column tables CT11 and CT12 according to the second exemplaryembodiment or the third exemplary embodiment may be stored in separatestorage areas or continuous storage areas. The column tables CT11 andCT12 may be incorporated into the header area of the storage area inwhich the entity data group is stored. The column tables CT31 and CT32according to the fourth exemplary embodiment may be stored in separatestorage areas or continuous storage areas, or they may be incorporatedinto the header area of the storage area in which the entity data groupis stored. Similarly, the intermediate identifier tables IT41 to IT43according to each of the fifth to seventh exemplary embodiments and thetenth exemplary embodiment may be stored in separate storage areas orcontinuous storage areas, or they may be incorporated into the headerarea of the storage area in which the entity data group is stored,similar to the intermediate identifier tables IT41 a to IT43 a accordingto the ninth exemplary embodiment.

As described above, the database according to each of the second, third,and fourth exemplary embodiments has a structure capable of dividing Ncolumns (N is an integer equal to or greater than 2) of tabular datainto one link table, N column tables, and an entity data group.Therefore, it is possible to perform a search process for each column ata high speed. The database according to the first exemplary embodimenthas a structure capable of dividing M (M is an integer equal to orgreater than 2) rows and N columns of tabular data into an identifiertable of M rows by N columns and an entity data group. Therefore, it ispossible to perform a search process for each column at a higher speedthan that in the databases according to the second, third, and fourthexemplary embodiments. Therefore, when N, the number of tabular datacolumns, is equal to or more than a predetermined value, it ispreferable to divide the tabular data into N column tables, a linktable, and an entity data group as in the second, third, or fourthexemplary embodiment, in order to improve the search speed for eachcolumn. When N, the number of tabular data columns, is equal to or morethan a predetermined value, it is preferable to divide the tabular datainto an identifier table of M rows by N columns and an entity data groupas in the first exemplary embodiment, in order to improve the searchspeed for each row.

The invention claimed is:
 1. A database system comprising: a storageunit that stores a database including an entity data group containing aplurality of entity data and a plurality of identifier tables havingonly a plurality of fixed-length data; and a data processing unit thatreceives a query and performs data processing on the database on thebasis of the received query, wherein each of the identifier tablesincludes at least one tuple that is defined in a row direction and atleast one attribute field that is defined in a column direction, storesa plurality of data identifiers uniquely indicating the plurality ofentity data as the fixed-length data, and has a data structurecorresponding to the at least one attribute field into which a tabulardata having a plurality of tuples including the plurality of dataidentifiers according to a plurality of attribute fields is divided, thedatabase further includes a link table that links corresponding tuplesbetween the identifier tables, and includes at least one tuple includingdata to link the plurality of data identifiers, which are stored in theidentifier tables, the plurality of data identifiers is stored in eachof the identifier tables sequentially, the data processing unit performsthe data processing using the link table and the identifier tables, thedatabase includes a plurality of sub-entity data having content relatedto the plurality of entity data, the identifier table further includessub-data identifiers that are in one-to-one correspondence with the dataidentifiers and uniquely indicate the sub-entity data, and whenselecting entity data from the entity data group by searching theidentifier table, the data processing unit reads sub-entity data havingcontent related to the selected entity data from the database using thesub-data identifiers.
 2. The database system according to claim 1,wherein a storage area allocated to the identifier table is differentfrom a storage area allocated to the entity data group.
 3. The databasesystem according to claim 1, wherein the values of the data identifiersare output values of a hash function that outputs a fixed-length bitstring when the entity data is input.
 4. The database system accordingto claim 1, wherein the attribute field of the link table includes anoffset designating the relative position of the storage area of thetuple of each of the identifier tables.
 5. The database system accordingto claim 1, wherein the attribute field of the link table includes apointer indicating an address allocated to the storage area of the tupleof each of the identifier tables.
 6. The database system according toclaim 1, wherein the attribute field of the link table includes anexternal tuple identifier that uniquely indicates the tuple of each ofthe identifier tables, each of the identifier tables includes aplurality of attribute fields, and one of the plurality of attributefields of each of the identifier tables includes a tuple identifier thatuniquely indicates the tuple of each of the identifier tables and has avalue corresponding to the external tuple identifier.
 7. The databasesystem according to claim 6, wherein the external tuple identifier is afixed-length bit string.
 8. The database system according to claim 1,wherein the database includes a conversion table indicating acorrespondence relation between pieces of position data indicating thestorage areas of the plurality of entity data and the plurality of dataidentifiers, and the data processing unit selects entity data from theentity data group using the conversion table and performs the dataprocessing on the basis of the selection result.
 9. The database systemaccording to claim 8, wherein the position data is an addressdesignating the absolute position of the storage area of the entitydata.
 10. The database system according to claim 8, wherein the positiondata is an offset designating the relative position of the storage areaof the entity data.
 11. The database system according to claim 1,wherein data identifiers for searching having the same values as theplurality of data identifiers are added to the plurality of entity data,and the data processing unit searches for the data identifiers forsearching, selects the entity data on the basis of the search result,and performs the data processing by using the selection result.
 12. Thedatabase system according to claim 1, wherein the plurality of entitydata includes variable-length data.
 13. The database system according toclaim 1, wherein the storage area allocated to the entity data group isdivided into a plurality of partition areas, and the plurality ofpartition areas is allocated as areas that store different types ofentity data in the entity data group.
 14. The database system accordingto claim 1, wherein the database includes a plurality of sub-entity datahaving content related to the plurality of entity data, the entity dataand the sub-entity data having content related to the entity data arestored in continuous storage areas, and when selecting entity data fromthe entity data group by searching the identifier table, the dataprocessing unit reads sub-entity data having content related to theselected entity data from the database.
 15. The database systemaccording to claim 1, wherein the database includes a plurality ofsub-entity data having content related to the plurality of entity data,a set of position data indicating the position of the storage area ofthe sub-entity data having content related to the entity data is addedto the entity data, and when selecting entity data from the entity datagroup by searching the identifier table, the data processing unit readssub-entity data designated by the position data added to the selectedentity data from the database.
 16. The database system according toclaim 15, wherein the position data indicating the position of thestorage area of the sub-entity data is an address designating theabsolute position of the storage area of the sub-entity data.
 17. Thedatabase system according to claim 15, wherein the position dataindicating the position of the storage area of the sub-entity data is anoffset designating the relative position of the storage area of thesub-entity data.
 18. The database system according to claim 1, whereinthe database includes at least one sub-entity data group having contentrelated to the entity data group, the storage unit includes a firststorage area allocated to the entity data group and a second storagearea allocated to the sub-entity data group, and the data processingunit selects one of the first storage area and the second storage areaon the basis of the received query.
 19. The database system according toclaim 1, wherein the query is described with a query language, and thedata processing unit analyzes the query and performs a transaction asthe data processing on the database on the basis of the analysis result.20. A method of managing a database, comprising: receiving a query for adatabase including an entity data group containing a plurality of entitydata and a plurality of identifier tables having only a plurality offixed-length data; and performing data processing on the database on thebasis of the received query, wherein each of the identifier tablesincludes at least one tuple that is defined in a row direction and atleast one attribute field that is defined in a column direction, storesa plurality of data identifiers uniquely indicating the plurality ofentity data as the fixed-length data, and has a data structurecorresponding to at least one attribute field into which a tabular datahaving said at least one tuple including the plurality of dataidentifiers according to a plurality of attribute fields is divided, thedatabase further includes a link table that links corresponding tuplesbetween the identifier tables, and includes at least one tuple includingdata to link the plurality of data identifiers, which are stored in theidentifier tables, the database is stored in a storage, the plurality ofdata identifiers is stored in each of the identifier tablessequentially, the data processing is performed using the link table andthe identifier tables, the database includes a plurality of sub-entitydata having content related to the plurality of entity data, theidentifier table further includes sub-data identifiers that are inone-to-one correspondence with the data identifiers and uniquelyindicate the sub-entity data, and when selecting entity data from theentity data group by searching the identifier table, the data processingunit reads sub-entity data having content related to the selected entitydata from the database using the sub-data identifiers.
 21. Anon-transitory computer-readable storage medium storing a program forcausing a computer to execute a database management process, thedatabase management process comprising: receiving a query for a databaseincluding an entity data group containing a plurality of entity data anda plurality of identifier tables having only a plurality of fixed-lengthdata; and performing data processing on the database on the basis of thereceived query, wherein each of the identifier tables includes at leastone tuple that is defined in a row direction and at least one attributefield that is defined in a column direction, stores a plurality of dataidentifiers uniquely indicating the plurality of entity data as thefixed-length data, and has data structure corresponding to the at leastone attribute field into which a tabular data having a plurality oftuples including the plurality of data identifiers according to aplurality of attribute fields is divided, the database further includesa link table that links corresponding tuples between the identifiertables, and includes at least one tuple including data to link betweenthe plurality of data identifiers, which are stored in the identifiertables, the plurality of data identifiers is stored in each of theidentifier tables sequentially, the data processing is performed usingthe link table and the identifier tables, the database includes aplurality of sub-entity data having content related to the plurality ofentity data, the identifier table further includes sub-data identifiersthat are in one-to-one correspondence with the data identifiers anduniquely indicate the sub-entity data, and when selecting entity datafrom the entity data group by searching the identifier table, the dataprocessing unit reads sub-entity data having content related to theselected entity data from the database using the sub-data identifiers.